Monster Media 1994 #2/Monster Media No. 2 (Monster Media)(1994).ISO/renegade/xcbv30.zip/XCBV.DOC

Text File | 1994-06-22 | 25KB | 531 lines

                       ╔════════════════════════════════╗
                       ║   Express Call-Back Verifier   ║
                       ║          Version 3.0           ║
                       ║  For Renegade Bulletin Boards  ║
                       ║  Copyright 1994 Phil Baggett   ║
                       ║      All Rights Reserved       ║
                       ╚════════════════════════════════╝


    FILE LIST
    ---------

    The Express Call-Back Verifier (XCBV) package consists of the following
    files:

        XCBV.DOC     - Main documentation
        HISTORY.DOC  - Program revision history
        INSTALL.BAT  - Installation utility
        UPGRADE.BAT  - Upgrade utility
        REGISTER.FRM - Registration form
        XCBVPACK.FLS - Packed program files
        HELPME.BAT   - Brief installation/upgrade instructions


    LICENSE
    -------

    XCBV is distributed as shareware. You may use this program for a trial
    period of 14 days; thereafter you must register with the author or
    discontinue use. See "REGISTRATION" near the end of this file.

    You may freely distribute this evaluation package so long as all files
    are unmodified and are included in each transfer. You may NOT
    distribute, by any means whatsoever, the "key" file you receive when you
    register (which is not part of this evaluation package).


    REQUIREMENTS
    ------------

    The DOS SHARE.EXE program must be in memory for this program to function
    properly under a multinode environment.

    This version of XCBV was developed for Renegade release 05-31-94.
    Compatibility with later versions is likely but not guaranteed, since
    Renegade's file structures may change. Before trying it, back up your
    user file, USERS.DAT, located in the DATA directory.

    I plan to continue to modify this program as needed to be compatible
    with future versions of Renegade if there's enough demand for it
    (registrations).


    INTRODUCTION
    ------------

    The Express Call-Back Verifier serves these main purposes:

        (1) Automatically upgrades users' access levels to predetermined
            values after successful verification.

        (2) Keeps a record of users' tested-and-verified phone numbers.

        (3) Allows SysOps to prevent users from calling under multiple user
            accounts.

    This CBV is quite different from others you may have used. Foremost is
    the simplicity involved in set-up and maintenance. You don't have to
    list all your local phone number prefixes. Neither do you have to rely
    on other add-on utilities to keep your call-back records up to date.

        ■  SysOps and Co-SysOps, whether running the door locally or from a
           remote location, can search through and edit the call-back
           database, which will contain each verified user's name, real
           name, phone number, and date of verification.

        ■  A special option is included for globally scanning and updating
           the call-back database, so SysOps can plug some or all users'
           current phone numbers into the database.

        ■  Customized text or ANSI files will be displayed at appropriate
           times when the door is being run, so you can give the program a
           personal touch.

        ■  Keeps a detailed log of all errors, call-back failures, and other
           noteworthy events (unless error logging is turned off).


    INSTALLATION
    ------------

    To install the program for the first time, run the INSTALL program and
    carefully follow the instructions. If you're upgrading from a previous
    version, run UPGRADE instead.

    -- Configuration --

    Run CONFIG.EXE to set up XCBV, and any time you need to make a change to
    any of the set-up options. (You must be in the directory where XCBV is
    installed.)  This configuration includes options that tell the program
    where your BBS files are, how to use your modem, and how you want to
    upgrade users.

    Next, use a text editor to modify the SPECIAL.TXT file. There are two
    sections in this file. First is the "Special Area Codes" section, where
    you need to list your local area code, as well as any other area codes
    that need to be specially handled. Beside each code, separated by a
    space, you can specify exactly what to dial before the phone number when
    calling users within that area. If you don't give a prefix, then only
    the user's actual number is dialed (###-####). Examples:

        404        <- For area code 404, just dial "###-####" (no prefix)
        234 8-     <- For 234, dial "8-###-####"
        567 9,567  <- For 567, dial "9,567###-####"

    Of course, for long-distance calls (if allowed), these numbers would be
    preceded by the long-distance prefix you established with CONFIG.EXE
    (usually "1-").

    Next is the "Illegal Dialing Sequences" section. Here you can list any
    sequences of digits that the program should not be allowed to dial as
    the first part of a number. Each line may contain a number sequence up
    to 14 digits. This feature provides a safeguard against users trying to
    cause the SysOp grief by making the verifier call the 911 emergency
    service, 976 or 1-900 toll numbers, etc.

    NOTE:  This feature was not intended to be used to "lock out" problem
           users. The easiest way to do that is explained later under "EDIT
           MODE".

    -- Display Files --

    Edit the special display files as desired (or create your own) to
    conform to your set-up. (You will need an ANSI editor, such as TheDraw,
    to change the ANSI screens.)  When the program needs to display one of
    these, it first looks for the filename with the .ANS extension, and if
    found, shows it as an ANSI display (if the user has ANSI). Otherwise, it
    looks for the .ASC extension and shows it. (This method is similar to
    how Renegade itself works.)  Note that Renegade color codes, as well as
    MCI codes, are NOT supported; use .ANS files if you want color.

    The display files (not including extensions) are:

        INTRO    - Displayed first, just after the program title and
                   copyright information.
        INUSE    - Displayed if someone's using the program on another node.
        NOTIME   - Displayed when user has less than the configured minimum
                   time remaining.
        NOLONGD  - Displayed to long-distance callers if long-distance
                   call-backs are not allowed, AND "auto-upgrade LD callers"
                   is disabled.
        AUTOUPLD - Displayed to long-distance callers if "auto-upgrade LD
                   callers" enabled, just before returning to BBS.
        BADNUM   - Displayed when user supplies a number that would cause an
                   illegal dialing sequence (described above), just before
                   giving him another try.
        PHONEDUP - Displayed when user's phone number is already recorded in
                   the call-back database under someone else's name.
        INSTRUCT - Displayed just before asking the user if he's ready to
                   disconnect for call-back.
        SUCCESS  - Displayed after successful verification.

    -- Renegade Set-Up --

    Inside Renegade, add a menu command that generates the appropriate
    dropfile type and runs the XCBV.BAT batch file with the %N (node number)
    and %# (user number) parameters. For example:

        Menu filename: MAIN
        Command #1 of 26

        1. Long descript :(=)Call-Back Verifier - For new users
        2. Short descript:(=)Call-Back Ver.
        3. Menu keys     :=
        4. ACS required  :"s255|(s30!s31)"
        5. Cmdkeys       :DW
        6. Options       :C:\BBS\DOORS\XCBV\XCBV.BAT %N %#
           Flags         :None
        Q. Quit

    NOTE:  Renegade must run the BATCH file, not XCBV.EXE directly.

    The above menu command would run the verifier when the user pressed the
    equals sign (=). Only users with a SL of either 255 (the SysOp) or 30
    (new user perhaps) could access the command. This example would create
    a CALLINFO.BBS dropfile and run XCBV.BAT, which is located in the XCBV
    program's main directory, C:\BBS\DOORS\XCBV.

    Instead of having the option on a displayed menu, as would be the case
    above, you might want to have Renegade automatically run the verifier if
    the user has a certain "new user" SL. Refer elsewhere for more
    information about Renegade's menu commands.

    Now, modify the included batch file, XCBV.BAT, as necessary, so that it
    changes to the program directory and executes the call-back program,
    passing the %1 and %2 parameters. For example:

        C:
        CD \BBS\DOORS\XCBV
        XCBV.EXE %1 %2


    PRELIMINARY NOTES
    -----------------

    Before you use this program, BACKUP YOUR USER FILE (USERS.DAT)!  This
    file should be located in your DATA directory. Although the program's
    been tested extensively, there are no guarantees. Be warned.

    The program will function locally (without a real carrier), but it still
    reads the BBS dropfile (see "INSTALLATION", "Renegade Set-Up"), and it
    still needs the BBS node number and user number parameters passed. For
    these reasons, testing is most easily accomplished by logging onto your
    BBS locally and running the verifier as a user would.

    When run in local mode, it will not attempt the actual call-back
    process. It runs through a simulated call-back, to allow you to see what
    users will see. Remote users with High Security Access can also do this.
    In a simulated call-back, nothing except program errors is written to
    the log file, and the phone number is never added to the database;
    however, the user's access is still "upgraded" as specified in your
    configuration.

    Disabling error logging is not recommend, at least until you have the
    program running smoothly. If a user reports that he received a "Fatal
    Error" message, and you weren't there to watch the error message, you'll
    need to check the log file. You'll also need to periodically check the
    log to make sure folks are not having problems getting verified. The
    most recent messages are listed at the bottom of the file. You can edit
    or delete the log file at any time if desired.

    As with all your important BBS files, you should backup the call-back
    database file (XCBV.DAT) regularly in case it somehow gets corrupted.

    If you have any problems getting the program to work properly, see
    "TROUBLESHOOTING" later in this document.


    USING THE PROGRAM
    -----------------

    Use of the program is fairly straightforward. When a user runs the
    program, it asks him whether he is long-distance. If he says yes, and
    the SysOp allows LD call-backs, the LD prefix is dialed before the
    number; if he says no and he's lying, the call shouldn't go through
    since the LD prefix is not used. If he says he's LD and LD call-backs
    are not allowed, a special file is displayed and the program exits back
    to the BBS.

    The program allows the user to correct his phone number (obtained from
    his BBS record) if necessary. If the user tries to make the verifier
    dial an illegal sequence (explained earlier), the attempt is recorded in
    the log file (if used), and the number is refused.

    If the program finds an existing call-back record for the user (same
    real name and phone number), the program assumes the user's BBS account
    was deleted, perhaps due to lack of activity, so it immediately upgrades
    the user and exits. For this reason, you should not allow users whom you
    purposely downgraded to run the verifier.

    After calling the user back, the program asks for the user's BBS
    password. If incorrect after 3 tries, the user is disconnected; if
    correct, the user's name, real name, and phone number are stored in the
    database, and the user is upgraded as specified in your configuration.
    After call-back, local callers are normally returned to the BBS and
    long-distance callers are disconnected to save on your phone bill.

    If verification fails, either because the program can't reconnect or the
    user failed the password check, the user's access is unchanged, and the
    reason for failure is written to the log file (if used).

    In cases where the program disconnects the user, upon returning to the
    board Renegade will detect a lost carrier, so there will be a "Hung up"
    entry in Renegade's SysOp log, which is normal.

    When a user can't complete call-back verification (because there's a
    duplicate phone number on record, he's calling LD and LD call-backs
    aren't allowed, etc.), you'll need to manually upgrade the user if you
    want to give him access.

    -- Upgrading Users --

    XCBV upgrades the user just as if you went to the user's account inside
    Renegade and validated him that way. Therefore, you'll probably want to
    set up a validation level (A-Z) in Renegade for users who complete
    call-back verification.

    Verified users are upgraded to the validation level you specified when
    you configured the program. Access settings such as Security Level (SL)
    and expiration date are set accordingly. When setting the user's AC and
    AR flags, these are adjusted according to whether your chosen
    verification level is specified as Hard or Soft.

    As with manual validation in Renegade's user editor, the number of
    credits the user has is increased by the number established for your
    verification level. For this reason, you normally should not allow a
    user to access the verifier more than once, since he could accumulate
    undeserved credits by running the program over and over, and each time
    XCBV would find his record, go ahead and upgrade him, and dump him back
    to the BBS.


    THE EDITOR
    ----------

    The Editor, EDIT.EXE, allows viewing/editing of the call-back database.
    As with XCBV.EXE, you must be in the main program directory before
    running the Editor. However, it can be run either at the DOS prompt or
    from your BBS, either from a local or remote logon. This allows you or
    any Co-SysOps to periodically check and maintain the database if
    desired.

    To start the Editor from the DOS prompt, simply go to the main program
    directory and run EDIT.EXE. Unless the node number is passed to the
    Editor program (i.e. "EDIT 1"), it runs in local mode. Running the
    Editor while inside your BBS requires a little preparation.

    -- Running the Editor from Your BBS --

    This section explains how to set up the Editor to be run from inside
    your BBS via a menu command. Although optional, this is handy if you
    frequently call your own board or have a Co-SysOp who is in charge of
    new user verification. If you intend to only run the Editor from the DOS
    prompt, feel free to skip this section.

    As with the XCBV.EXE program, the Editor should be run from a batch file
    if it is to be accessed while logged onto your BBS. Create a Renegade
    menu command similar to the one that runs XCBV.BAT. Here's an example:

        Menu filename: MAIN
        Command #1 of 26

        1. Long descript :(/E) CBV Editor - View/edit CBV database
        2. Short descript:(/E) CBV Editor
        3. Menu keys     :/E
        4. ACS required  :"s255"
        5. Cmdkeys       :DW
        6. Options       :C:\BBS\DOORS\XCBV\EDIT.BAT %N
           Flags         :None
        Q. Quit

    NOTE:  Renegade must run the BATCH file, not EDIT.EXE directly, and must
           pass the %N (node number) parameter.

    Now modify the included batch file, EDIT.BAT, as necessary, so that it
    changes to the program directory and executes the Editor, passing the %1
    parameter. For example:

        C:
        CD \BBS\DOORS\XCBV
        EDIT.EXE %1


    USING THE EDITOR
    ----------------

    Inside the Editor, you can go to a specific record number, search for a
    certain record by partial user name, real name, or phone number, and
    make any desired changes. Most commands on the menus are
    self-explanatory. Note that you can usually abort an operation by just
    hitting ENTER at the prompt.

    When running searches on the database, the Editor will find records that
    contain the given string of characters. For example, if you're looking
    for Samantha Golden's record, you could search for "Sam" or "Gold" in
    the Real Name field.

    If you want to "lock out" a certain phone number, simply add a call-back
    record to the database. For the user name, you might want to enter
    something like "LOCKED"; for the phone number, enter the number you
    want "locked out". (This method allows you to search for "LOCKED" in the
    user name field to view/edit all your lock-outs.)


    ADDING NUMBERS FROM YOUR BBS USER FILE
    --------------------------------------

    One option that deserves further explanation, the "Scan & update
    records" option, was included so that you could have a fairly accurate
    and complete record of all your current users' phone numbers when you
    first install the verifier, without forcing all current users to run it.
    USE THIS WITH CAUTION, because indiscriminate use will cause undesired
    additions to the database. If the verifier has already upgraded a
    substantial number of people, you might want to backup the database just
    before using this option.

    With this option, you can scan for certain user names, certain security
    levels, or all users. It searches through your BBS user file and adds
    them (you can confirm each addition if desired). Keep in mind that the
    numbers in Renegade's user file are users' voice numbers, so in some
    cases the number added to the call-back database may not be the user's
    data line.

    You're also given the option of checking for duplicate accounts while
    scanning. If you choose to do so, then as each user's account is
    scanned, the Editor makes sure there are no other records with the same
    phone number already in the call-back database. Although this option
    takes longer, it helps you track down false user accounts.

    The Editor reports (on screen and to the log file, if used) any
    duplicate phone numbers it finds (when the users' real names don't
    match). Remember that these may in fact be separate individuals who
    reside in the same household, so you'll have to decide what to do about
    their access (voice verification perhaps). In the case of duplicates,
    the one already in the call-back database will remain there, and the
    duplicate in the user file is not added.

    Remember, the "Scan & update records" option should normally only be
    needed once -- when you first install the verifier -- if you use it at
    all. After that, the verifier will keep a lookout for duplicate numbers
    as each user tries to get verified.


    TROUBLESHOOTING
    ---------------

    This section was included to help solve common problems that occur while
    using (or trying to use) this program. If you're still having problems
    after looking over this section, please don't hesitate to contact the
    author or another SysOp that uses this program.

    First of all, an improper configuration can be the cause of many errors,
    so run CONFIG and check EVERY set-up option first. Also check the
    SPECIAL.TXT file for errors in syntax or format. Another general
    suggestion is to make sure you followed all installation instructions to
    the letter. Here are some common problems and their causes:

    ■■■  Program reports "Error opening BBS user/system file(s)"

      The only known cause for this error is an incorrect setting for your
      "BBS Main Directory". Run CONFIG and make sure this is set to the
      directory where RENEGADE.DAT is located.

    ■■■  Reports "Error accessing BBS dropfile..."

      The program can't find the dropfile. This error has several causes:

      1. You're running the program from outside Renegade (the DOS command
         line), and a dropfile doesn't exist in the proper place. Try
         running it from a menu while logged onto your board.

      2. The dropfile type you specified in the configuration is not the
         same as the one Renegade created. If you use CALLINFO.BBS, then
         your Cmdkeys field in your menu command should be DW.

      3. Your "System Configuration" -> "Modem/Node Configuration" -> "Path
         for door files" setting is blank or otherwise incorrect. Make sure
         this is set to the path where you want dropfiles (such as
         CALLINFO.BBS) created when your doors are run. Do this for EACH
         NODE if you're running a multi-node system.

    ■■■  Reports "Error opening NODEx.DAT"

      The program doesn't find the indicated file where expected. Under
      "System Config" -> "Main BBS Configuration", make sure the "RAM
      drive/multinode path" points to the location of your NODE*.DAT files.

    ■■■  Reports "Change to the directory where XCBV is installed..."

      The main program, XCBV.EXE, was not run from your XCBV directory.
      Make sure the Options field of your Renegade menu command specifies
      the full path to your batch file, and that your batch file changes to
      your XCBV directory FIRST, and then runs XCBV.EXE. Renegade should
      NOT run the .EXE directly, but rather the BATCH file.

    ■■■  Program doesn't correctly upgrade a user

      One known cause of this problem is a corrupted USERS.DAT. Generally
      speaking, if XCBV can ever upgrade ANY user, it is functioning
      properly with your version of Renegade.

      First try deleting USERS.IDX so that Renegade will recreate a fresh
      index file, and then restart your BBS and run the verifier. If the
      problem persists, a possible solution is to retrieve USERS.DAT from
      your most recent backup, delete the .IDX file again, and give it a
      try. It's recommended that you first rename your current USERS.DAT in
      case this suggestion doesn't help.


    CONTACTING THE AUTHOR
    ---------------------

    Thanks for trying this program, and if you have any comments, questions,
    or problems, please let me know. The quickest way to reach me is to
    call my BBS:

                                    BETATRON
                                 [phone]
                           Located in Atlanta, Georgia

    If you prefer or can't seem to access my BBS, please write to this
    address:

        Phil Baggett
        2775 NE Expressway, #3-1
        Atlanta, GA  30345


    REGISTRATION
    ------------

    XCBV is the result of many hours of hard work, and your support is
    necessary to ensure the future of the program. When you register,
    you'll receive a "key" file that you copy to your XCBV directory to
    remove the sign-off shareware notice from the program. This "key" will
    register future versions as well, unless I change the registration
    requirements. The registration cost is $20.

    -- How to Register --

    Use the included REGISTER.FRM file and follow the directions therein.
    In addition to the key file, the disk you receive will include the
    latest version of the program. Remember, you may NOT distribute the key
    file you receive in any manner whatsoever.


    DISCLAIMER
    ----------

    The Author, Phil Baggett, hereby disclaims all warranties, express or
    implied, concerning this software. The Author shall not be liable for
    any damage caused by this software (whether or not he is aware that such
    damage may occur) and shall not be liable for errors in any part of the
    software documentation. Furthermore, the Author is not obligated to
    continue to update or otherwise modify the program in any way.

    By using this software, the user agrees to the above terms.

                                    <<END>>